What do we know about successful software project factors

This dissertation discusses how different practitioners define project success and success factors for software projects and products. The motivation for this work is to identify the way software practitioners’ value and define project success. This can have implications for both practitioner motivation and software development productivity. Accordingly, in this work, we are interested in the various perceptions of the term “success” for different software practitioners and researchers. To get this information we performed a systematic mapping of the recent year’s software development literature trying to identify stakeholders’ perceptions about the success of a project and also possible differences among the views of the various stakeholders of a project. Some common terms related to project success (success project; software project success factors) were considered in formulating the search strings. The results were limited to twenty-two selected peer-reviewed conferences, papers/journal articles, published between 2003 and 2012

What Works Better? A Study of Classifying Requirements

Classifying requirements into functional requirements (FR) and non-functional ones (NFR) is an important task in requirements engineering. However, automated classification of requirements written in natural language is not straightforward, due to the variability of natural language and the absence of a controlled vocabulary. This paper investigates how automated classification of requirements into FR and NFR can be improved and how well several machine learning approaches work in this context. We contribute an approach for preprocessing requirements that standardizes and normalizes requirements before applying classification algorithms. Further, we report on how well several existing machine learning methods perform for automated classification of NFRs into sub-categories such as usability, availability, or performance. Our study is performed on 625 requirements provided by the OpenScience tera-PROMISE repository. We found that our preprocessing improved the performance of an existing classification method. We further found significant differences in the performance of approaches such as Latent Dirichlet Allocation, Biterm Topic Modeling, or Naive Bayes for the sub-classification of NFRs.Comment: 7 pages, the 25th IEEE International Conference on Requirements Engineering (RE'17

Looking for the Holy Grail of Software Development

The history of Software Engineering has been marked by many famous project failures documented in papers, articles and books. This pattern of lack of success has prompted the creation of dozens of software analysis, requirements definition, and design methods, programming languages, software development environments and software development processes all promoted as solving ?the software problem.? What we hear less about are software projects that were successful. This article reports on the findings of an extensive analysis of successful software projects that have been reported in the literature. It discusses the different interpretations of success and extracts the characteristics that successful projects have in common. These characteristics provide Software Project Managers with an agenda of topics to be addressed that will help ensure, not guarantee, that their software project will be successful

Antibiotic Resistance and RAPD-PCR Genotyping of Pseudomonas aeruginosa Clinical Strains Isolated from Intensive Care Unit Patients

Background: Pseudomonas aeruginosa is one the most important nosocomial pathogens, especially in immunocompromised patients. Identifying the source of contamination in health centers plays an important role in the control of hospital infections. The aim of this study was to determine antibiotic susceptibility and genetic patterns of P. aeruginosa isolated from patients hospitalized in intensive care unit of Masih Daneshvari Hospital, Tehran, Iran. Materials and Methods: Antibiotic susceptibility of the isolates was examined through 10 antibiotics recommended by Clinical and Laboratory Standards Institute (CLSI, 2018) guidelines using the Kirby-Bauer disc diffusion method. Random amplified polymorphic DNA (RAPD) analysis with the short primer of 272 was used to evaluate genetic relationship among the isolates and the results were analyzed by Gelcompar II software. Results: Of the antibiotics used, the most sensitive was found in colistin (96.4%) and the highest resistance rates were observed in cefotaxime (94.6%), chloramphenicol (83.9%) and imipenem (71.4%). DNA fingerprinting was able to identify 12 genetic patterns by RAPD-PCR technique. Conclusion: Antibiotic resistance in isolates of P. aeruginosa is rising and there is possibility of occurring outbreaks in the medical centers. Different sources of strains show their constant exchange via intra- and extra-hospital transmission routes. Thus, according to the data of this study, there is a serious need to control sources of infections by physicians and staff when they are working in several sectors to control and prevent the transmission of the bacterium

Effect of Intermediate-Dose vs Standard-Dose Prophylactic Anticoagulation on Thrombotic Events, Extracorporeal Membrane Oxygenation Treatment, or Mortality among Patients with COVID-19 Admitted to the Intensive Care Unit: The INSPIRATION Randomized Clinical Trial

Importance: Thrombotic events are commonly reported in critically ill patients with COVID-19. Limited data exist to guide the intensity of antithrombotic prophylaxis. Objective: To evaluate the effects of intermediate-dose vs standard-dose prophylactic anticoagulation among patients with COVID-19 admitted to the intensive care unit (ICU). Design, Setting, and Participants: Multicenter randomized trial with a 2 � 2 factorial design performed in 10 academic centers in Iran comparing intermediate-dose vs standard-dose prophylactic anticoagulation (first hypothesis) and statin therapy vs matching placebo (second hypothesis; not reported in this article) among adult patients admitted to the ICU with COVID-19. Patients were recruited between July 29, 2020, and November 19, 2020. The final follow-up date for the 30-day primary outcome was December 19, 2020. Interventions: Intermediate-dose (enoxaparin, 1 mg/kg daily) (n = 276) vs standard prophylactic anticoagulation (enoxaparin, 40 mg daily) (n = 286), with modification according to body weight and creatinine clearance. The assigned treatments were planned to be continued until completion of 30-day follow-up. Main Outcomes and Measures: The primary efficacy outcome was a composite of venous or arterial thrombosis, treatment with extracorporeal membrane oxygenation, or mortality within 30 days, assessed in randomized patients who met the eligibility criteria and received at least 1 dose of the assigned treatment. Prespecified safety outcomes included major bleeding according to the Bleeding Academic Research Consortium (type 3 or 5 definition), powered for noninferiority (a noninferiority margin of 1.8 based on odds ratio), and severe thrombocytopenia (platelet count <20 �103/µL). All outcomes were blindly adjudicated. Results: Among 600 randomized patients, 562 (93.7) were included in the primary analysis (median interquartile range age, 62 50-71 years; 237 42.2% women). The primary efficacy outcome occurred in 126 patients (45.7%) in the intermediate-dose group and 126 patients (44.1%) in the standard-dose prophylaxis group (absolute risk difference, 1.5% 95% CI,-6.6% to 9.8%; odds ratio, 1.06 95% CI, 0.76-1.48; P =.70). Major bleeding occurred in 7 patients (2.5%) in the intermediate-dose group and 4 patients (1.4%) in the standard-dose prophylaxis group (risk difference, 1.1% 1-sided 97.5% CI,-� to 3.4%; odds ratio, 1.83 1-sided 97.5% CI, 0.00-5.93), not meeting the noninferiority criteria (P for noninferiority >.99). Severe thrombocytopenia occurred only in patients assigned to the intermediate-dose group (6 vs 0 patients; risk difference, 2.2% 95% CI, 0.4%-3.8%; P =.01). Conclusions and Relevance: Among patients admitted to the ICU with COVID-19, intermediate-dose prophylactic anticoagulation, compared with standard-dose prophylactic anticoagulation, did not result in a significant difference in the primary outcome of a composite of adjudicated venous or arterial thrombosis, treatment with extracorporeal membrane oxygenation, or mortality within 30 days. These results do not support the routine empirical use of intermediate-dose prophylactic anticoagulation in unselected patients admitted to the ICU with COVID-19. Trial Registration: ClinicalTrials.gov Identifier: NCT04486508. © 2021 American Medical Association. All rights reserved

A Magnet-and-Spring Based Visualization Technique for Enhancing the Manipulation of Requirements

Requirements engineers model the system of interest from different points of view by creating numerous artifacts. Although they have to deal with a great amount of information, the display space of the devices is limited. This limitation leads to a time consuming navigation through the artifacts. Requirements engineers have to scroll through numerous pages and switch between multiple windows. However, they have to rely on their memory when there is no space left on the screen to view another piece of relevant information. In this research, we propose to develop a novel visualization technique that flexibly creates editable views of a linked set of elements or artifacts where the pieces show different levels of detail according to the user’s demand for the current task. Thus, important parts are shown in detail, while the space taken for displaying unimportant parts is minimized. Our conceptual solution is a combination of the focus+context concept and a magnet-and-spring system. The focus+context concept is responsible for resizing and relocating objects to make space for more relevant information. The magnet-and-spring system is responsible for distributing the distortion caused by the focus+context concept throughout the workspace, such that the distorted view of the information looks more natural. Considering the artifacts of a software development project as a single hypothetical artifact enables us to manage the artifacts in the same way we deal with the objects inside an artifact. Our envisaged tool support should be embeddable in requirements applications and bring its benefits to the applications manipulating requirements artifacts

ImitGraphs: towards faster usability tests of graphical model manipulation techniques

Due to the increasing use of general purpose graphical models (e.g., UML diagrams) and domain specific graphical models in different stages of software development, software engineers who work with these models spend more time interacting with modeling tools. Thus, the usability of interaction techniques of modeling tools affects the overall productivity of software development. Tool developers and user interface designers rely on the feedback from usability tests to optimize the user interface of tools that provide a graphical editor. Developing a working prototype to test new techniques is costly due to the complexity and variety of graphical models. This results in either tests at the late stages of development when changes are more expensive, or tests with prototypes that only support a subset of the intended graphical models, thus not comprehensive. In order to simplify conducting usability tests, instead of using the intended graphical models in the tests, we propose to use simpler models that require similar interactions when being manipulated. For this purpose, we introduced ImitGraphs, an extended graph with additional properties so that it can be specialized in interacting similarly to an intended graphical model. Then, we designed a method to instruct test participants to create ImitGraphs. Specialized graphs enable us to develop prototypes for usability tests faster and consequently cheaper resulting in more usability tests at early stages of tool development and on a wider range of intended models

Challenges of working with artifacts in requirements engineering and software engineering

When developing or evolving software systems of non-trivial size, having the requirements properly documented is a crucial success factor. The time and effort required for creating and maintaining non-code artifacts are significantly influenced by the tools with which practitioners view, navigate and edit these artifacts. This is not only true for requirements, but for any artifacts used when developing or evolving systems. However, there is not much evidence about how practitioners actually work with artifacts and how well software tools support them. Therefore, we conducted an exploratory study based on 29 interviews with software practitioners to understand the current practice of presenting and manipulating artifacts in tools, how practitioners deal with the challenges encountered, and how these challenges affect the usability of the tools used. We found that practitioners typically work with several interrelated artifacts concurrently, less than half of these artifacts can be displayed entirely on a large screen, the artifact interrelationship information is often missing, and practitioners work collaboratively on artifacts without sufficient support. We identify the existing challenges of working with artifacts and discuss existing solutions proposed addressing them. Our results contribute to the body of knowledge about how practitioners work with artifacts when developing or evolving software, the challenges they are faced with, and the attempts to address these challenges